NMS SS7 provides a standard program to read the SS7 (including SCCP) configuration from a set of text files and download the configuration to the SS7 tasks running on the TX board. Refer to the NMS SS7 Configuration Manual for more information.
The SCCP layer supports the following configuration entities:
Configuration |
Description |
General |
The general configuration defines the operational parameters of the SCCP layer: resource allocations, timer values, and threshold values. The general configuration is loaded only once at system boot time and must be loaded before any other configuration entities. |
User SAPs |
One user service access point (SAP) is defined for each application using the SCCP layer services. A user SAP is associated with a single subsystem number and switch type (ANSI or ITU-T). The user SAP defines whether the application is replicated on another node for reliability purposes, and lists any concerned point codes (for example, nodes that must be notified of any change in the status of the application). User SAPs are initially loaded at system boot time. Additional user SAPs can be added later, up to the maximum specified in the general configuration. |
Network SAPs |
One network service access point (NSAP or network SAP) is defined for each MTP 3 layer interface that the SCCP layer uses. Typically the SCCP layer has only a single network SAP, although if the same system supports multiple switch types (ANSI and ITU-T), the SCCP layer would have a separate network SAP for each switch type. |
Routes |
One route is defined for each destination subsystem that the SCCP layer can access. The route defines the destination point code used to reach that subsystem as well as any backup point code that replicates the subsystem. Routes are initially loaded at system boot time. Additional routes can be added later, up to the maximum specified in the general configuration. |
Addresses |
Address entries define how the SCCP layer is to translate and/or route between global titles, point codes, and subsystem numbers. Address translations are initially loaded at system boot time. Additional address translations can be added later, up to the maximum specified in the general configuration. |
The following illustration shows the relationship between the various configurable entities: